Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

swapping python version to 3.11 #1411

Merged
merged 26 commits into from
Jun 5, 2024
Merged

swapping python version to 3.11 #1411

merged 26 commits into from
Jun 5, 2024

Conversation

BryonLewis
Copy link
Collaborator

@BryonLewis BryonLewis commented Mar 4, 2024

  • Swap from 3.8 to 3.10 to enable 3.11.
  • Convert to using 3.11 docker base images where possible
  • Update Project.toml to update girder and large-image references
  • Refactor worker container based on the kitware/viame docker container to install 3.11 and utilize it. Reminder that large-image tasks run on the main container and not in the worker.

TODO:

  • Update Vue to 2.7 and remove dependency on Vue Composition API in preparation for the eventual upgrade to 3.0
  • Update vuetify to a newer (2.X) version
  • Confirm Building individual versions still works (library, web, electron).

"@typescript-eslint/no-unused-vars": "off",
"vue/no-template-target-blank": "off",
"vue/no-lone-template": "off",
"default-param-last": "off",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a fan of default-param-last. Could we just disable it inline if it's needed for API stability reasons in a few places?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I updated the base eslint rules there were a bunch of new issues being thrown. This one was small enough I can resolve it fairly quickly. Most instances were older functions with default params that required more params added for newer features. There were only a few instances so I removed this and added in sane defaults.


const useVuetify = () => {
const vm = getCurrentInstance();
return vm?.proxy?.$vuetify || undefined;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it reasonable at runtime for this function to return undefined, or does that mean something unexpected has gone wrong?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call, If this is undefined it should error out. I'll update to throw an error.

zachmullen
zachmullen previously approved these changes Jun 4, 2024
zachmullen
zachmullen previously approved these changes Jun 4, 2024
@BryonLewis BryonLewis merged commit d6b6e05 into main Jun 5, 2024
4 checks passed
@BryonLewis BryonLewis deleted the python-311-update branch June 5, 2024 19:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants